Skip to content

chore: configure Copilot - #568

Closed
efraespada wants to merge 1 commit into
masterfrom
setup/copilot/6085c0e6-fe64-492f-81b8-90213b759225
Closed

efraespada wants to merge 1 commit into
masterfrom
setup/copilot/6085c0e6-fe64-492f-81b8-90213b759225

Conversation

@efraespada

@efraespada efraespada commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

Adds reviewed Copilot setup configuration and workflows for agent CLI provisioning and optional credential health checks. The setup PR is awaiting human review and merge; runner access, credentials, and runtime behavior remain unverified.

What changed

  • Records the selected manual self-hosted runner profile and setup operation metadata.
  • Adds a dispatchable workflow that checks configured agent CLIs and their command-line interfaces.
  • Adds optional, provider-specific credential checks that avoid printing credential values.
  • Excludes setup-generated branches from the commit workflow trigger and normalizes workflow syntax.
  • Stores replaced repository files as setup backups and formats issue template labels.

Validation

  • The PR body reports 0 pending capacity, 4 runner access checks unverified, and 3 missing assets.
  • Runtime credential and capability verification remain pending; no completed check results were provided.

Review notes

  • Review the generated workflows, repository guidance, runner profile, and setup backups before merging.
  • Human merge, runner access, agent authentication, and trusted workflow verification are still pending.

@vypbot

vypbot commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

Bugbot: review complete

Current status: No active findings on 74bdb19.

Pull request · Verified commit · Workflow run

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.37%. Comparing base (5b0dd52) to head (74bdb19).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #568      +/-   ##
==========================================
- Coverage   93.38%   93.37%   -0.01%     
==========================================
  Files         897      897              
  Lines       27930    27930              
  Branches     8126     8126              
==========================================
- Hits        26082    26081       -1     
  Misses        733      733              
- Partials     1115     1116       +1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@efraespada

Copy link
Copy Markdown
Member Author

Real #556 dogfooding completed the reviewed batch Apply and recovered the same prepared commits after superseding older installer PRs. This PR remains unmerged and blocked: #570 reproduces that the source workflow validator rejects the setup-generated {group, labels} runner route, including with current develop. Published master additionally predates the credential-health routing exception. Checks have not been weakened or bypassed.

The exact generated route passed in GitHub for platform: provisioning run, runner group vypdev, runner ubuntu-runner-2. Configuration and Codex runner authentication also passed.

The before/after comparison found all six organization/repository Variable and Secret metadata inventories unchanged. Both installation manifests, complete commit parents, branch heads and PR identities matched their private operation receipts. No permission-cleanup journal or operation lock remains. The local setup session is closed and the temporary PAT copy has been removed; the operator has been told it can be revoked.

A separate dogfood bug, #569, records normal automation triggered by the disposable permission-probe refs. Seven exact owned probe runs were cancelled after checking their actor, branch, commit and creation time. No unrelated run was cancelled. These findings must be handled through the normal issue/Action-managed branch flow; this installer branch contains only its reviewed setup assets.

@vypbot

vypbot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

Copilot approval · Human review needed

Status: Only open, non-draft, complete same-repository pull requests are eligible.
Completed: 0/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 74bdb19399bb; base: 5b0dd52f2af9; reason: unsupported-pr.

@efraespada

Copy link
Copy Markdown
Member Author

Superseded by the reviewed v3.6.0 dogfooding operation b0260a9e-59ee-40a1-b904-0a9214564a84. The original immutable head 74bdb19 and installation receipt were verified before closure. The branch and commit are retained; no merge or branch deletion is requested.

@efraespada efraespada closed this Oct 19, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in vypdev Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants